home *** CD-ROM | disk | FTP | other *** search
PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) NNNNAAAAMMMMEEEE ppppmmmmvvvviiiieeeewwww++++ - configuration file format for performance metrics 3D visualization back-end DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN This man page describes version 2.1 of ppppmmmmvvvviiiieeeewwww++++ configuration file format, which is the extention of ppppmmmmvvvviiiieeeewwww(1) configuration format version 2.1. The configuration format supports metrics from multiple hosts or archives. A configuration file can specify metrics without a source, with different hosts and different archives. However, a configuration file that contains archives may only have one archive for anyone host. When in ``replay'' mode, any metrics with host specific sources require an archive to be specified for that host on the command line or as a source to a previous metric. The archive must be the same archive (based on a string comparison of the archive names) of any archives specified in the configuration file for the same host. The time controls will list all hosts that are specified on the command line and the configuration file in the timezone listing (see ppppmmmmttttiiiimmmmeeee(1)). The configuration file format is based on a two-dimensional grid which can contain a variety of bars, stacks, links, pipes, labels and other grids. The grids resize each column and row to match the size of the largest item in that column or row. A configuration file that contains only one object does not require a grid. The ppppmmmmvvvviiiieeeewwww++++ configuration file starts with an identification header in the first non-comment line: pmview Version 2.1 [_c_o_m_m_a_n_d__l_i_n_e] The optional _c_o_m_m_a_n_d__l_i_n_e should be the command line with which the tool was launched, if the configuration file has been generated by another tool. This is useful for applications that are to be restarted automatically on the next login, after the user has logged out while ppppmmmmvvvviiiieeeewwww++++ was still running. Care should be taken to ensure that the command specified is either a full pathname or will be found on the PATH available at login. All lines which begin with ``#'' are treated as comments and ignored. Otherwise, all spaces, tabs and newlines are treated as white space so multiple commands may be on the same line. The syntax for specifying values in the configuration file is consistent for all commands, namely: _c_o_l_o_r A color must be either a XXXX(1) color name, a XXXX(1) numerical color, or three normalized _r_e_a_l values representing the saturation of red, green and blue. For example, the following colors are identical: PPPPaaaaggggeeee 1111 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) red rgbi:1.0/0.0/0.0 1.0 0.0 0.0 _i_n_t An integer. _m_e_t_r_i_c A metric consists of an optional source (host or archive), the metric name, an optional instance list immediately after name, followed by the maximum (or normalization value). A colon (``:'') is used to separate a host name from the metric, and a forward slash (``/'') to separate an archive name from the metric. Instances are enclosed in square brackets and comma separated. Each instance may be enclosed in quotes. For example, some legal metrics are: kernel.all.cpu.idle 4000 myhost:kernel.all.cpu.idle[cpu0,"cpu3"] 1000.0 /path/to/myarchive/kernel.all.cpu.idle[cpu1] 1000 To assist the process of matching instance names, two further comparisons are made beyond a simple string comparison. If the instance name contains spaces, only the first word in the instance name is required to match the instance, assuming that the first word is unique. If the first word is not unique, only the first matching instance will be selected. The second comparison occurs if the first word is a number with leading zeros. Any leading zeros will be skipped before comparing the first word again. This permits process ids used in the _p_r_o_c metrics to be easily matched, without specifying the entire instance name. For example, to visualize the user and system time of _i_n_i_t use the metric specification proc.psusage.utime[1] 1000 proc.psusage.stime[1] 1000 _n_a_m_e A name for an object which may be referred to later in the configuration file. Names must be a single word consisting of all alphanumeric characters, as well as underscores, dashes and colons. It is recommended that names do not begin with an underscore as this may be interpreted as a keyword. _p_o_s This is the position of the object within the grid. The syntax of a position is: [ [_x _z] [ [_w_i_d_t_h _d_e_p_t_h] [_a_l_i_g_n_m_e_n_t] ] ] _x The horizontal coordinate (left to right) of the object, starting at 0. The default _x is 0. PPPPaaaaggggeeee 2222 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) _z The vertical coordinate (top to bottom) of the object, starting at 0. The default _z is 0. _w_i_d_t_h The number of columns occupied by the object. The default _w_i_d_t_h is 1. _d_e_p_t_h The number of rows occupied by the object. The default _d_e_p_t_h is 1. _a_l_i_g_n_m_e_n_t The edge or corner that the object is aligned with. Possible alignments include: _n_o_r_t_h, _s_o_u_t_h, _e_a_s_t, _w_e_s_t, _n_o_r_t_h_e_a_s_t, _n_o_r_t_h_w_e_s_t, _s_o_u_t_h_e_a_s_t, _s_o_u_t_h_w_e_s_t and _c_e_n_t_e_r. Abbreviations like _s_e and _S_E are also accepted. The default alignment is _c_e_n_t_e_r. The size of an object may not be known as the number of instances for some metrics will vary between hosts and PMDA configurations. Therefore, the position of the object can be used to specify the likely size of the object, so that the position of the surrounding objects is appropriately adjusted. The following are legal positions: 0 5 The object is centered at grid position 0,5 occupying 1 grid square. 1 2 north The object is aligned with the north edge of position 1,2 occupying 1 grid square. 2 2 2 1 east The object is aligned to the eastern edge of position 3,2 and occupies 2 grid squares (2,2 and 3,2). _s_t_r_i_n_g A string is a series of characters enclosed in double quotes. A string may not contain newlines or escaped double quotes. There are several parameters that may affect the size, shape and color of objects when they are displayed. These parameters are scoped so that they only alter objects defined later in the same scope. Therefore, parameter settings at the top of a configuration file affect the entire scene, unless they are changed later in the file. Most of these parameters are also resources. ____bbbbaaaarrrrLLLLeeeennnnggggtttthhhh _i_n_t The side length of the ____bbbbaaaarrrr and ____ssssttttaaaacccckkkk blocks. Default is 28. PPPPaaaaggggeeee 3333 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) ____bbbbaaaarrrrHHHHeeeeiiiigggghhhhtttt _i_n_t The maximum height of a ____bbbbaaaarrrr and ____ssssttttaaaacccckkkk blocks. Default is 80. ____bbbbaaaasssseeeeCCCCoooolllloooorrrr _c_o_l_o_r The color of ____bbbbaaaarrrr, ____ggggrrrriiiidddd and ____ssssttttaaaacccckkkk base planes. Default is rgbi:0.15/0.15/0.15. ____bbbbaaaasssseeeeHHHHeeeeiiiigggghhhhtttt _i_n_t The height of ____bbbbaaaarrrr, ____ggggrrrriiiidddd and ____ssssttttaaaacccckkkk base planes. Default is 2. ____ggggaaaappppWWWWiiiiddddtttthhhh _i_n_t The gap between blocks in a ____bbbbaaaarrrr object in the X-axis. The default is 8. ____ggggaaaappppDDDDeeeepppptttthhhh _i_n_t The gap between blocks in a ____bbbbaaaarrrr object in the Z-axis. The default is 8. ____ggggaaaappppLLLLaaaabbbbeeeellll _i_n_t The gap between the base of a ____bbbbaaaarrrr object, and any metric or instance labels. The default is 6. ____ggggrrrriiiiddddWWWWiiiiddddtttthhhh _i_n_t The minimum width of a ____ggggrrrriiiidddd column. The default is 20. ____ggggrrrriiiiddddDDDDeeeepppptttthhhh _i_n_t The minimum depth of a ____ggggrrrriiiidddd row. The default is 20. ____llllaaaabbbbeeeellllMMMMaaaarrrrggggiiiinnnn _i_n_t The margin around a ____llllaaaabbbbeeeellll object. The default is 5. ____llllaaaabbbbeeeellllCCCCoooolllloooorrrr _c_o_l_o_r The color of ____llllaaaabbbbeeeellll and ____bbbbaaaarrrr labels. The default is white. ____mmmmaaaarrrrggggiiiinnnnWWWWiiiiddddtttthhhh _i_n_t The extra width of a ____bbbbaaaarrrr, ____ggggrrrriiiidddd and ____ssssttttaaaacccckkkk base plane beyond the objects on the plane. The default is 8. ____mmmmaaaarrrrggggiiiinnnnDDDDeeeepppptttthhhh _i_n_t The extra depth of a ____bbbbaaaarrrr, ____ggggrrrriiiidddd and ____ssssttttaaaacccckkkk base plane beyond the objects on the plane. The default is 8. ____ppppiiiippppeeeeLLLLeeeennnnggggtttthhhh _i_n_t Total length of a ____ppppiiiippppeeee.... The default is the value of ____bbbbaaaarrrrHHHHeeeeiiiigggghhhhtttt.... ____ssssccccaaaalllleeee _r_e_a_l The scale applied to the entire scene. This parameter may not be used within any objects, only at the top of the configuration file. The default is 1.0. PPPPaaaaggggeeee 4444 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) To simplify the specification of colors, a ____ccccoooolllloooorrrrLLLLiiiisssstttt and a ____ccccoooolllloooorrrrSSSSccccaaaalllleeee may be used to define colors for an object which has metrics associated with it, i.e. ____bbbbaaaarrrr, ____ssssttttaaaacccckkkk or ____ppppiiiippppeeee. A color list may be defined within an object, or named and defined at the top of a configuration file. A named color list may then be referenced within multiple objects: ____ccccoooolllloooorrrrLLLLiiiisssstttt _n_a_m_e (((( _c_o_l_o_r [_c_o_l_o_r...] )))) Associate the _c_o_l_o_rs with the color list _n_a_m_e. The assignment of colors to blocks depends on the type of an object. For example, the color list called _f_o_o has the same color three times: _colorList foo ( red rgbi:1.0/0.0/0.0 1.0 0.0 0.0 ) ____ccccoooolllloooorrrrSSSSccccaaaalllleeee _n_a_m_e _c_o_l_o_r (((( _c_o_l_o_r _r_e_a_l [_c_o_l_o_r _r_e_a_l...] )))) Associate the _c_o_l_o_rs and _r_e_a_ls with the color list _n_a_m_e. The initial _c_o_l_o_r is the default color of the object. The object will change color to the other colors when the normalized value of the object is equal to or greater than each _r_e_a_l. Therefore, each _r_e_a_l must be larger than the previous _r_e_a_l, and should be in the range 0.0 to 1.0. This scale gradually changes from blue to red: _colorScale coldToHot blue ( rgbi:0.5/0.0/1.0 0.3 purple 0.6 rgbi:1.0/0.0/0.5 0.8 red 0.95) There are several different object types which could be found in a ppppmmmmvvvviiiieeeewwww++++ scene: ____bbbbaaaarrrr, ____ssssttttaaaacccckkkk, ____ppppiiiippppeeee, ____ggggrrrriiiidddd, ____lllliiiinnnnkkkk, and ____llllaaaabbbbeeeellll. There is also ____xxxxiiiinnnngggg which is a special type of the ____lllliiiinnnnkkkk. The ____bbbbaaaarrrr, ____ssssttttaaaacccckkkk and ____ppppiiiippppeeee objects are modulated by metric values, a ____llllaaaabbbbeeeellll is fixed text, ____lllliiiinnnnkkkk and ____xxxxiiiinnnngggg are interconnects and a ____ggggrrrriiiidddd is a container of objects, including other ____ggggrrrriiiidddd objects, which controls the layout of the scene. A ____ggggrrrriiiidddd object is only required if there are two or more objects in the scene. ____bbbbaaaarrrr, ____ggggrrrriiiidddd and ____ssssttttaaaacccckkkk objects may have base planes which provide a point of reference for the blocks as they change height. A label can be applied to the base plane ____ggggrrrriiiidddd object if it is ____sssshhhhoooowwwwnnnn with: ____bbbbaaaasssseeeeLLLLaaaabbbbeeeellll _n_a_m_e|_s_t_r_i_n_g ____bbbbaaaasssseeeeLLLLaaaabbbbeeeellll should be used within the scope of the relevant ____bbbbaaaarrrr, ____ggggrrrriiiidddd or ____ssssttttaaaacccckkkk object. The first ``\n'' characters in the string will be replaced by a new line. Subsequent ``\n'' characters will be ignored. For a scene to be valid it must contain at least one modulated object. The objects are defined as: PPPPaaaaggggeeee 5555 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) ____bbbbaaaarrrr [_o_p_t_i_o_n_s] (((( [_m_e_t_r_i_c-_l_i_s_t] [_c_o_l_o_r-_l_i_s_t] [_l_a_b_e_l-_l_i_s_t] )))) A ____bbbbaaaarrrr object represents a collection of blocks. The number of blocks depends on the number of metrics and metric instances assigned to the object. By default, the blocks are modulated by changing the height of each block. Alternatively, blocks may be modulated by changing color, or both height and color. Each color in the _c_o_l_o_r- _l_i_s_t is assigned to each metric. Therefore, multiple instances of the one metric will have the same color. The _o_p_t_i_o_n_s that may be passed to a ____bbbbaaaarrrr object are: _p_o_s The position of the ____bbbbaaaarrrr object within the current ____ggggrrrriiiidddd object. ____ccccoooollll|____rrrroooowwww Position the blocks so that each instance is in a column (____ccccoooollll) or a row (____rrrroooowwww). This implies that each different metric is in a separate row or column, respectively. The default is ____ccccoooollll. ____sssshhhhoooowwww|____hhhhiiiiddddeeee Is the base plane visible? Default is ____sssshhhhoooowwww. ____yyyymmmmoooodddd|____ccccoooolllloooorrrrmmmmoooodddd|____ccccoooolllloooorrrryyyymmmmoooodddd Modulate the blocks by adjusting their height (____yyyymmmmoooodddd), color (____ccccoooolllloooorrrrmmmmoooodddd) or both height and color (____ccccoooolllloooorrrryyyymmmmoooodddd). ____ccccuuuubbbbeeee|____ccccyyyylllliiiinnnnddddeeeerrrr Set the shape of the blocks. The default is ____ccccuuuubbbbeeee. ____ggggrrrroooouuuuppppbbbbyyyymmmmeeeettttrrrriiiicccc|____ggggrrrroooouuuuppppbbbbyyyyiiiinnnnsssstttt|____ggggrrrroooouuuuppppbbbbyyyyrrrroooowwww|||||ggggrrrroooouuuuppppbbbbyyyyccccoooollll Set the grouping of blocks when launching other tools. For tools like ppppmmmmcccchhhhaaaarrrrtttt(1) some views may generate many small charts which cannot be drawn entirely within the screen. Another problem is it may be more appropriate to generate charts with the same instance in each chart, rather then the same metric. The group specifiers control the algorithm used so that a separate chart will be drawn for each ____mmmmeeeettttrrrriiiiccccssss specification (____ggggrrrroooouuuuppppbbbbyyyymmmmeeeettttrrrriiiicccc), for the first, second etc. instance of each ____mmmmeeeettttrrrriiiicccc (____ggggrrrroooouuuuppppbbbbyyyyiiiinnnnsssstttt), or by the rows and columns of the ____bbbbaaaarrrr object depending on ____rrrroooowwww or ____ccccoooollll. The default is ____ggggrrrroooouuuuppppbbbbyyyymmmmeeeettttrrrriiiicccc. The options must be specified in this order, although preceding options are not required. Therefore, this is legal: _bar _hide _cylinder ( ... ) The metrics, colors and labels are specified within the brackets in any order. Only the _m_e_t_r_i_c-_l_i_s_t is mandatory. _m_e_t_r_i_c-_l_i_s_t A ____bbbbaaaarrrr metric list contains a list of metric names, normalization values and an optional label for the metric: ____mmmmeeeettttrrrriiiiccccssss (((( _m_e_t_r_i_c _r_e_a_l [_s_t_r_i_n_g] [_m_e_t_r_i_c _r_e_a_l [_s_t_r_i_n_g]...] )))) PPPPaaaaggggeeee 6666 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) _c_o_l_o_r-_l_i_s_t A ____bbbbaaaarrrr color list may be a named color list that was defined earlier, or an unnamed color list. A ____ccccoooolllloooorrrrSSSSccccaaaalllleeee list should be used when using ____ccccoooolllloooorrrrmmmmoooodddd or ____ccccoooolllloooorrrryyyymmmmoooodddd modulation. Therefore, the syntax for color lists within a ____bbbbaaaarrrr object are any of: ____ccccoooolllloooorrrrLLLLiiiisssstttt _n_a_m_e ____ccccoooolllloooorrrrLLLLiiiisssstttt (((( _c_o_l_o_r [_c_o_l_o_r...] )))) ____ccccoooolllloooorrrrSSSSccccaaaalllleeee _n_a_m_e ____ccccoooolllloooorrrrSSSSccccaaaalllleeee _c_o_l_o_r (((( _c_o_l_o_r _r_e_a_l [_c_o_l_o_r _r_e_a_l...] )))) _l_a_b_e_l-_l_i_s_t In addition to labels for each metric in the _m_e_t_r_i_c-_l_i_s_t, metric and instance labels may be defined using ____mmmmeeeettttrrrriiiiccccllllaaaabbbbeeeellllssss and ____iiiinnnnssssttttllllaaaabbbbeeeellllssss statements. The position of the labels around the ____bbbbaaaarrrr object depends on the ____rrrroooowwww or ____ccccoooollll orientation of metrics and instances, and whether the label is read ____ttttoooowwwwaaaarrrrddddssss the ____bbbbaaaarrrr object, or ____aaaawwwwaaaayyyy. The default is ____ttttoooowwwwaaaarrrrddddssss. ____mmmmeeeettttrrrriiiiccccllllaaaabbbbeeeellllssss [____aaaawwwwaaaayyyy|____ttttoooowwwwaaaarrrrddddssss] (((( _n_a_m_e|_s_t_r_i_n_g [_n_a_m_e|_s_t_r_i_n_g...] )))) ____iiiinnnnssssttttllllaaaabbbbeeeellllssss [____aaaawwwwaaaayyyy|____ttttoooowwwwaaaarrrrddddssss] (((( _n_a_m_e|_s_t_r_i_n_g [_n_a_m_e|_s_t_r_i_n_g...] )))) ____ggggrrrriiiidddd [_p_o_s] [____sssshhhhoooowwww|____hhhhiiiiddddeeee] (((( _o_b_j_e_c_t_s )))) A ____ggggrrrriiiidddd object is a container for objects, including other ____ggggrrrriiiidddd objects. The rows and columns of a ____ggggrrrriiiidddd object are resized to the largest object in the row or column. If an object spans multiple rows and/or columns, those rows and columns may be partly resized to contain the object. However, the resizing of rows and columns for objects occupying multiple rows and columns occurs after resizing for objects occupying only one grid square. A collision between objects occupying the same squares will be reported as an error message and the later object will be ignored. The options to a ____ggggrrrriiiidddd object control the position (_p_o_s) of the ____ggggrrrriiiidddd object in the parent ____ggggrrrriiiidddd, and indicate whether to ____sssshhhhoooowwww or ____hhhhiiiiddddeeee the ____ggggrrrriiiidddd base plane. By default, the base plane is hidden. The parameters described above may be specified within the brackets of a ____ggggrrrriiiidddd object, however they only apply to the objects within the ____ggggrrrriiiidddd, not the ____ggggrrrriiiidddd itself. For a parameter to be applied to a ____ggggrrrriiiidddd object, it must be specified before the ____ggggrrrriiiidddd object declaration. ____llllaaaabbbbeeeellll [_o_p_t_i_o_n_s] _s_t_r_i_n_g A ____llllaaaabbbbeeeellll object draws the contexts of _s_t_r_i_n_g at the location, orientation and size specified in the _o_p_t_i_o_n_s: PPPPaaaaggggeeee 7777 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) _p_o_s The position of the ____llllaaaabbbbeeeellll object in the current ____ggggrrrriiiidddd object. ____lllleeeefffftttt|____rrrriiiigggghhhhtttt|____uuuupppp|____ddddoooowwwwnnnn The orientation of the _s_t_r_i_n_g. The direction indicates the direction the label is read. Therefore, ____rrrriiiigggghhhhtttt is the default since the string is read from left to right. ____ssssmmmmaaaallllllll|____mmmmeeeeddddiiiiuuuummmm|____llllaaaarrrrggggeeee The font size. The default is ____mmmmeeeeddddiiiiuuuummmm. ____lllliiiinnnnkkkk _p_o_s [_s_t_r_i_n_g] A ____lllliiiinnnnkkkk object draws a straight or L-shaped horizontal round ``pipe'' with diameter equal to 80% of the __b_a_s_e_H_e_i_g_h_t of an enclosing ____ggggrrrriiiidddd. The properties of the object are defined by the options: _p_o_s sets both the position of the ____lllliiiinnnnkkkk on the grid and its shape. ____lllliiiinnnnkkkk starts in the column and row on the ____ggggrrrriiiidddd specified by first two numbers in the _p_o_s and spans the number of columns and rows set by the second two numbers. The _a_l_i_g_n_m_e_n_t value is used to decide the orientation of the link (links are always aligned at the center): _e_a_s_t and _w_e_s_t links are straight and going from left to right, _n_o_r_t_h and _s_o_u_t_h links are straight and going from far end of the grid to near end, _n_o_r_t_h_e_a_s_t, _n_o_r_t_h_w_e_s_t, _s_o_u_t_h_e_a_s_t and _s_o_u_t_h_w_e_s_t links are L-shaped and connect the corresponding points of the compass, i.e. a _n_o_r_t_h_e_a_s_t link takes on the general shape of the Latin letter ``L''. _s_t_r_i_n_g sets the ``tag'' for the ____lllliiiinnnnkkkk which will be displayed in the text window when the pointer is over the link. ____ppppiiiippppeeee _p_o_s (((( [_m_e_t_r_i_c-_l_i_s_t] [_c_o_l_o_r-_l_i_s_t] [_t_a_g] )))) A ____ppppiiiippppeeee object represent a set of cylinders, placed on top of each other and oriented parallel to the base plane. The diameter of a ____ppppiiiippppeeee is equal to 80% of __b_a_s_e_H_e_i_g_h_t. The number of blocks is dependent on the number of metric instances in the _m_e_t_r_i_c-_l_i_s_t. The colors in the _c_o_l_o_r-_l_i_s_t are assigned in turn to each cylinder in the ____ppppiiiippppeeee. The length of the ____ppppiiiippppeeee is defined by the __p_i_p_e_L_e_n_g_t_h. _p_o_s defines the position of the ____ppppiiiippppeeee on the enclosing ____ggggrrrriiiidddd and its orientation with _a_l_i_g_n_m_e_n_t field used to define at which end of the pipe to stack the colored cylinders. The cylinders are stacked at the corresponding point of the compass and the pipe's direction is from the point of the compass towards the center of the compass. Only _e_a_s_t, _w_e_s_t, _n_o_r_t_h, and _s_o_u_t_h are valid values for the pipe's alignment. PPPPaaaaggggeeee 8888 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) The metrics, colors and label may be specified within the brackets in any order. Only the _m_e_t_r_i_c-_l_i_s_t is mandatory. _m_e_t_r_i_c-_l_i_s_t A ____ppppiiiippppeeee metric list contains a list of metric names and normalization values: ____mmmmeeeettttrrrriiiiccccssss (((( _m_e_t_r_i_c _r_e_a_l [_m_e_t_r_i_c _r_e_a_l...] )))) _c_o_l_o_r-_l_i_s_t A ____ppppiiiippppeeee color list may be named color list that was defined earlier, or an unnamed color list: ____ccccoooolllloooorrrrLLLLiiiisssstttt _n_a_m_e ____ccccoooolllloooorrrrLLLLiiiisssstttt (((( _c_o_l_o_r [_c_o_l_o_r...] )))) _t_a_g A ____ppppiiiippppeeee may have a ``tag'' for the filler block (unanimated block on the ``other'' end of the pipe) which will be displayed in the text window when the pointer is over that end of the pipe. ____ppppiiiippppeeeeTTTTaaaagggg _n_a_m_e|_s_t_r_i_n_g ____ssssttttaaaacccckkkk [_o_p_t_i_o_n_s] (((( [_m_e_t_r_i_c-_l_i_s_t] [_c_o_l_o_r-_l_i_s_t] [_l_a_b_e_l] )))) A ____ssssttttaaaacccckkkk object represents a set of blocks placed vertically on top of each other. The number of blocks is dependent on the number of metric instances in the _m_e_t_r_i_c-_l_i_s_t. The colors in the _c_o_l_o_r-_l_i_s_t are assigned to each block in the ____ssssttttaaaacccckkkk. By default, the height of the ____ssssttttaaaacccckkkk will be the sum of the height of each block. The _o_p_t_i_o_n_s that may be passed to a ____ssssttttaaaacccckkkk object are: _p_o_s The position of the ____ssssttttaaaacccckkkk object within the current ____ggggrrrriiiidddd object. ____sssshhhhoooowwww|____hhhhiiiiddddeeee Is the base plane visible? Default is ____sssshhhhoooowwww. ____uuuuttttiiiillllmmmmoooodddd|____ffffiiiillllllllmmmmoooodddd Force the height of the stack to always be the maximum height. This is achieved by normalizing the height of each block (____uuuuttttiiiillllmmmmoooodddd), or by adding a grey block to the top of the stack (____ffffiiiillllllllmmmmoooodddd). ____ccccuuuubbbbeeee|____ccccyyyylllliiiinnnnddddeeeerrrr Set the shape of the blocks. The default is ____ccccuuuubbbbeeee. The options must be specified in this order, although preceding options are not required. Therefore, this is legal: _stack 1 1 _north _utilmod ( ... ) PPPPaaaaggggeeee 9999 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) The metrics, colors and label may be specified within the brackets in any order. Only the _m_e_t_r_i_c-_l_i_s_t is mandatory. _m_e_t_r_i_c-_l_i_s_t A ____ssssttttaaaacccckkkk metric list contains a list of metric names and normalization values: ____mmmmeeeettttrrrriiiiccccssss (((( _m_e_t_r_i_c _r_e_a_l [_m_e_t_r_i_c _r_e_a_l...] )))) _c_o_l_o_r-_l_i_s_t A ____ssssttttaaaacccckkkk color list may be named color list that was defined earlier, or an unnamed color list: ____ccccoooolllloooorrrrLLLLiiiisssstttt _n_a_m_e ____ccccoooolllloooorrrrLLLLiiiisssstttt (((( _c_o_l_o_r [_c_o_l_o_r...] )))) _l_a_b_e_l A ____ffffiiiillllllllmmmmoooodddd type ____ssssttttaaaacccckkkk may have a label for the filler block: ____ssssttttaaaacccckkkkLLLLaaaabbbbeeeellll _n_a_m_e|_s_t_r_i_n_g ____xxxxiiiinnnngggg _c_o_l _r_o_w _c_o_l_u_m_n_s _r_o_w_s _d_i_r_1 ... _d_i_r_4 A ____xxxxiiiinnnngggg is a special kind of link which is used to draw a pair of links which cross each other. To convey the visual impression that the links do not join, one of the links is drawn as a ``broken'' cylinder. _c_o_l and _r_o_w define the position on the enclosing grid. _c_o_l_u_m_n_s and _r_o_w_s define the size of the bounding box. The end points of the crossing cylinders are placed exactly in the center of the corner cells of the bounding box and four small cylinders or stubs are used to join the perimeter of the bounding box with the end points on the crossing cylinders. Four _d_i_r values define the orientation of the stubs, starting at the upper left corner of the ____xxxxiiiinnnngggg and proceeding clockwise, such that respective stubs are used to join the point of the compass with the center on the cell (see example). EEEEXXXXAAAAMMMMPPPPLLLLEEEE This simple example illustrates the use of parameters and different object types: pmview Version 2.1 # Use a lighter grey for the base planes _baseColor rgbi:0.5/0.5/0.5 # Define colors for CPU object _colorList cpu ( blue2 red2 yellow2 cyan2 green2 ) # The top grid object, but hide it from view _grid _hide ( PPPPaaaaggggeeee 11110000 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) # Show the current load in a bar object _bar 0 0 ( _baseLabel "Load averages over a\n1, 5 and 15 minute interval" _metrics ( kernel.all.load[1] 1 "1" kernel.all.load[5] 1 "5" kernel.all.load[15] 1 "15" ) _colorList ( blue blue blue ) ) # Add a label below the load bars _label 0 1 "Load" # Change the color of the base plane for later objects _baseColor pink # Show the CPU usage over all CPUs in a utilization stack _stack 2 0 _south _utilmod ( _baseLabel "CPU Utilization over all CPUs" _metrics ( kernel.all.cpu.user 1000 kernel.all.cpu.sys 1000 kernel.all.cpu.intr 1000 kernel.all.cpu.wait.total 1000 kernel.all.cpu.idle 1000 ) _colorList cpu ) # Add a label below the CPU stack _label 2 1 "CPU" # Create a separate grid for links and pipes _marginWidth 1 _marginDepth 1 _gridSpace 12 _grid 0 3 5 4 _hide ( _pipeLength 12 _baseHeight 12 # Add a pipe and a link with western orientation _pipe 0 0 west ( _pipeTag "West pipe" _metrics ( kernel.all.cpu.user 1000 kernel.all.cpu.sys 1000 kernel.all.cpu.idle 1000 ) _colorList cpu ) PPPPaaaaggggeeee 11111111 PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) PPPPMMMMVVVVIIIIEEEEWWWW++++((((4444)))) _link 0 2 west "West link" # Add xing _xing 1 0 3 3 west east east west # Add a link and a pipe with eastern orientation _pipe 4 0 east ( _pipeTag "East Pipe" _metrics ( kernel.all.cpu.user 1000 kernel.all.cpu.sys 1000 kernel.all.cpu.idle 1000 ) _colorList cpu ) _link 4 2 east "East link" ) ) SSSSEEEEEEEE AAAALLLLSSSSOOOO ppppmmmmvvvviiiieeeewwww(1) and ppppmmmmvvvviiiieeeewwww++++(1). PPPPaaaaggggeeee 11112222 
